Sets a read/write append/consume buffer that can be accessed by the specified compute shader.
Append/consume buffers are inherently read/write buffers since both the Append and Consume functions serve to change the resource.
Take note that append/consume buffers can only be either appended (stack-like push operation) to or consumed (stack-like pop operation) from in the same shader stage.
They can however be swapped around between shaders so that one consumes the data in such a buffer while another shader appends new data to it.

You can bind up to 8 different buffer and image resources for read/write access by a compute shader on DX11 hardware. These will use registers u0 through u7.
Only a single read/write resource can be bound at any one time on DX10 hardware (to register u0).
Take note that buffers and textures (as well as render targets, but those aren't applicable to the compute shader; if you use read/write resources in a pixel shader they share slots with render targets
as well however) share the same register slots, thus setting a buffer to slot 1 followed by setting a texture to the same slot will overwrite the previously set buffer.
You can unbind buffers by specifying nullptr as the buffer argument; this is neccessary if the same buffer is bound as a read-only buffer by the same shader since a resource cannot simultaneously
be bound for read-only and read/write access (you can read from the read/write resource as the name suggests though).
Append/consume buffers are declared like so in HLSL:

• AppendStructuredBuffer BufferName : register(t?) where ? ranges between 0 and 7 (only slot 0 is available on DX10 hardware) for append/consume buffers that will be appended by the shader


• ConsumeStructuredBuffer BufferName : register(t?) where ? ranges between 0 and 7 (only slot 0 is available on DX10 hardware) for append/consume buffers that will be consumed by the shader